Systems and Methods to Facilitate Selling of Products and Services

ABSTRACT

The system of the present invention provides systems and methods for selling goods and services on, over, through, and in conjunction with the Internet. The system receives session (clickstream) information on a customer&#39;s website session from the enterprise&#39;s website and may also receive customer information on the customer from the enterprise&#39;s CRM or eCRM system. The session information referred to comprises the goods or services the customer is searching and metadata about such search and the relevant products, such as the surfing pattern itself. The system determines from the received information, based on the interaction between matching rules created using the system by the enterprise and the system&#39;s matching engine, whether the customer is a candidate for assistance from a sales associate. The system creates and indexes information on available sales associates and their performance, selling capabilities and product expertise. The system further matches the customer with at least one sales associate, ideally the most appropriate sales associate, based on the customer, session, and sales profile associate information, and facilitates communication between the sales associate and the customer. Additionally, the system provides information on the customer, products or services the customer is interested in, and the collateral sales materials (both internal and external to the enterprise) and selling techniques to the sales associate based on the particular sales opportunity. The system facilitates communication between the sales associate and the customer on the basis of chat, voice over IP, email and the public switched telephone network, including the concept of bridging a chat session into a PSTN conference call during which call the sales associate and customer maintain a co-browsing session with regard to the opportunity over the Internet.

FIELD OF THE INVENTION

The present invention relates generally to electronic commerce, and more particularly to methods and systems to facilitate selling interactions that originate online

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to U.S. application Ser. No. 09/922,753, filed Aug. 6, 2001, which claims priority to U.S. provisional application Ser. No. 60/244,039, filed Oct. 26, 2000, which documents are incorporated herein by this reference.

BACKGROUND OF THE INVENTION

Electronic commerce, or “e-commerce,” as it is commonly referred to, involves the sales of goods or services over, through or in conjunction with the Internet. Currently, e-commerce largely concerns the sale of goods or services that are relatively simple in terms of the product variability and complexity. Most e-commerce today derives from one of just a few categories of goods that meet this test of simplicity: books, compact discs, flowers and travel (mainly just airline seats). E-commerce is restricted to these categories of goods today largely because the goods themselves are simple enough that they can be presented in an catalog format. The customer does not need to consult with an expert in these goods or services before purchasing them. Thus, almost all Internet e-commerce sites today are sterile, pure self-service environments.

The complexity and variability of goods and services that sell online is increasing as greater numbers of enterprises of those goods seek to leverage the distributional efficiencies of the Internet. The increase in the complexity and variability of goods and services requires an increase in the consultative nature of the sales experience for the customer.

For example, in the travel category, most online purchasing activity currently relates to airline seats. When purchasing airline seats a customer has essentially two variables to deal with: (i) flight schedule and (ii) price. Otherwise, one airline seat is generally the same as any other. However, as the enterprises seek to sell exotic, luxury travel packages, such as safaris to Africa or boat trips through the Amazonian Rainforest over the Internet, the variables and the complexity of the sales process increases dramatically. For such a sale, a customer will want to know where to stay, what kinds of food to eat (and what kinds not to eat), whether the territory is considered dangerous or the trip is considered rigorous, whether special inoculations are required, and other complex questions. These questions demonstrate the added variety and complexity of the inputs necessary for the customer to make an informed purchase decision for this kind of service and they fundamentally require human interaction with a knowledgeable sales agent or product specialist to be answered in a meaningful way. The same type of complexity is inherent in the purchase of a variety of other goods and services including banking services (mortgages, retail banking, wealth planning), insurance services, electronics, luxury retail goods (fine watches, jewelry) and automobiles. Sale of these products requires a “trusted relationship” between a customer and a live sales expert who can use proven internal and external resources as collateral sales material to close the sale. Fundamentally, these products are sold, not just dropped in a shopping cart and purchased.

In the offline world today, purveyors of these complex goods and services strive to create comfortable retail environments in which knowledgeable personnel politely answer customers' questions about product and service features, capabilities and alternatives, facilitate sales, and upsell related products and services, such as service warranties. For example, when shopping for a camera in an offline store, sales associate will guide the customer toward the right camera, sell additional lenses, a case, batteries, a warranty, and perhaps some film before physically walking the customer to the cash register and closing the sale. E-commerce environments, by contrast, are almost completely self-service environments, notwithstanding the existence of chat platforms and other technologies that facilitate online interaction.

It is clear that there is a much higher level of interaction in the physical world. Customers have come to expect that there will be someone available in a physical location that can answer questions about products and direct them through the process. It is also frequently the case that a high-end shopper from a wealthy demographic is matched with a sales associate who, though otherwise skilled in the product to be sold, is mismatched with the demographic and psychographic characteristics of the buyer.

As enterprises attempt to increase the type and volume of goods and services bought through an online origination, the availability of knowledgeable expertise and assistance and relevant sales collateral materials must be addressed in order to persuade customers that they can obtain enough product-centric information to make buying over, through or in conjunction with the online channel an easy, pleasant experience that is equal or superior to shopping through other channels. Moreover, the Internet fundamentally changes the way goods and services are bought by customers. In the offline world, customers go to a store to buy a product; online, customers seek a product first, and then identify a store from which it can be purchased.

While a number of companies have extended existing call center technology into Internet sales environments in order to enable live voice or chat sessions with browsing customers, the Internet retail experience is still largely sterile and unsatisfying. Rather, the current online interaction focuses on customer service rather than sales—a significant distinction as customer services personnel are not well-suited to closing sales.

“Customer relationship management” (“CRM” or, as adopted for the online world, “eCRM”) solutions providers have existed for several years now. However, few if any of these solutions facilitate meaningful, direct human interaction through the online channel. In fact, many CRM solutions that have offered call center support for catalogs and have simply extended their product offering to include Frequently Asked Questions (“FAQ”), e-mail and chat features that most of the eCRM companies have in common. Many eCRM enterprises have thus chosen to focus on facilitating “touchless” e-commerce transactions, i.e., transactions that do NOT require human intervention.

Online chat or instant messaging is the most personalized and sophisticated mode of customer/sales associate interaction. Using platforms developed by companies like AOL, these programs facilitate real-time online chat between the two parties, occasionally allowing the sales representative to “push” web pages or content to the customer in order to guide the customer to products or information. Some eCRM companies take this one step further by offering voice over IP. With voice over IP, if the customer has the right equipment on her computer she can talk to a customer service representative via the Internet. Most of the programs require the customer to log in to the chat session, allowing the customer service representative to maintain a history of customer contact. Some of the programs also allow the sales associate to view the complete customer purchase and communication history. Again, however, these platforms are typically staffed by customer service representatives and not sales associates and do not involve any “matching” of the right agent with the customer based on the agent's profile and skills, the customer's demographic and psychographic characteristics and the nature of the browsing opportunity.

FAQ services use historical “common” inquiries to generate template responses to customer questions. Some products go a step further and use artificial intelligence to analyze customer inquiries and generate “smart” answers. E-mail products also use gateway screening or artificial intelligence to answer customer questions in a more efficient manner than having a customer service representative personally respond to each question. Some e-mail programs also add direct e-mailing capabilities that can target and customize e-mail campaigns according to historical customer data. Some eCRM providers have product configurator applications. With these applications a customer is provided with a variety of questions regarding the features of the product they are interested in. Based on the answers to the questions the application will provide a suggestion as to the best configuration of the product for the customer. This solution is still a “touchless” experience from the standpoint of human interaction.

In general, CRM is reactionary—generally focused on post sale activity, such as, keeping existing customers, resolving problems, and managing customer relationships. CRM representatives are generalists, with no specific product or sales knowledge. By comparison, sales is proactive—focused on pre-sale activity, such as, obtaining customers, avoiding problems, creating customer relationships, and assisting customers in the purchase of goods or services. Sales associates are trained in the art of selling and posses specific and in-depth knowledge about goods and services.

A system does not exist that (i) matches browsing customers with experienced, knowledgeable sales personnel, (ii) provides relevant, opportunity-centric sales collateral information to the sales personnel and then (iii) facilitates the type of interaction between the customer and the sales person that is familiar in the offline world.

SUMMARY OF THE INVENTION

The present invention addresses the current lack of online sales assistance by creating the infrastructure to establish a system that allows accredited, experienced and product-knowledgeable sales personnel to sell goods and services (collectively, “products”), particularly complex, highly-consultative products, more effectively over, through, or in conjunction with online channels. The terms “over, through or in conjunction with the Internet,” used singly or in combination, contemplate sales that occur through the present invention that (i) are effected solely through online interaction, as well as sales that occur through the present invention that merely originate online or (ii) are captured online, such as through the present invention, but are consummated either through a telephone connection (as contemplated herein) or in an offline (face-to-face) setting. With regard to the scenarios contemplated in item (ii) above, the present invention represents a bridge that connects online and offline selling.

The present invention fundamentally changes the Internet purchasing experience from one akin to browsing in a catalog to one similar to purchasing goods or services in the offline world with real time access to people who are knowledgeable in the goods or services being purchased and skilled in the art of closing a sale. Moreover, the present invention provides the sales personnel with product information from the enterprise and third parties. The present invention further monitors each sale and accumulates a record of effective sales techniques and information. The present invention further provides real-time communication functionality, via Internet chat, voice over IP, Internet streaming and the public switched telephone network (“PSTN”), that facilitates live and effective communication between the sales associate (“SA”) and the customer. The present invention may be implemented by an enterprise either on a standalone basis or on a basis that is integrated (heavily or lightly) with other applications that operate in reference to an enterprise's Internet site (such as a one-to-one marketing application), or an enterprise's existing CRM, inventory, accounting or enterprise resource planning (“ERP”) systems.

The present invention allows enterprises (whether principally online or offline in nature and heritage) to bring their existing sales force into contact with online browsers to further the enterprise's ultimate objective—generating more revenue, irrespective of where a given ‘lead’ originates. The present invention further allows a new paradigm to emerge by permitting sales associates to leverage their expertise in selling certain specific products for multiple providers of those products (e.g., for the sales associate to offer his expertise on a product-centric, rather than an enterprise-centric basis). A veritable army of available, highly qualified, independent sales associates (functioning as independent contractors with regard to the enterprise that sells the relevant product) may be unleashed by the present invention on an infinite number of live sales opportunities. Alternatively, the instant invention could be deployed within the paradigm commonly existing today—within a ‘captive’ sales force of existing employees of the enterprise, again allowing those employees to leverage their sales expertise on a product-centric basis.

The present invention is for use in connection with the Internet environment, whether wired or wireless, or can be used with other environments now and in the future. The present invention has application in offline environments as well. For example, the database of experienced mortgage agents created by the invention could be accessed by other mortgage agents within the enterprise (or by the enterprise's management or Human Relations department) to gather information as to who would be the best agent for the first agent to collaborate with on a given offline opportunity. Similarly, agents could use the database of sales collateral materials and their proven effectiveness in given situations to address a customer's objection expressed in an offline, face to face meeting. Thus, there are both offline and online applications and utilities of the present invention. Within this application, the word website shall generically mean any electronic interface to the enterprise and includes, but is not limited to, a website on the World Wide Web accessed via a computer or wireless device with a browser functionality and also includes any other electronic interface where a enterprise's goods or services can be purchased, including an Internet-enabled telephone or voice response system.

The system of the present invention provides SAs with interactive tools that allow them to emulate, as closely as possible, the interaction between customers and sales personnel that are commonly accepted in the offline world. The closer the online experience reflects its offline counterpart, the quicker consumers will adopt the online channel as an adjunct to existing channels. The system of the present invention performs several major tasks. First, the system provides a registration system for all SAs that enables the system to keep track of all SAs and allows for a credit and background check on the SA, if desired. The system also provides online training, education, and accreditation procedures that enable SAs to establish their competency to sell specific types and categories of products or services and to sell online in general (e.g., it measures the SAs online proficiencies, ability to type, ability to navigate the Web, etc.). The system determines whether a customer browsing on a website needs sales assistance based upon available clickstream and/or login data (the login data, for example, might identify the customer as a high-net worth individual who either already is or is eligible to become a ‘private banking’ client). The system also allows the customer either to ask for sales assistance or to be proactively approached with sales assistance by an SA who is accredited by the system to sell that product and who has been made aware of the opportunity by the opportunity-matching parameters of the system.

As noted above, the system includes a matching engine. The matching engine dynamically matches SAs with online customers based on a variety of enterprise and/or system-driven criteria in order to ensure that the most qualified SA is matched with each customer (based on known data about the browsing session (the nature of the opportunity), the customer and the agent and his or her rankings, permissions and ratings as defined by the registration module). The relevant matching criteria are varied and include clickstream data, demographic characteristics of the browser passed through login information or cookies, etc. The system permits the enterprise that is operating it to establish and weight these opportunity-matching parameters to achieve the best matches possible based on past experience with the system's or the enterprise's sales and marketing objectives. The matching engine additionally dynamically changes the matching criteria based on various factors, such as sales successes or changing market conditions. The matching engine ranks the SAs based on the matching criteria used and generates a list of SAs in rank order. The rules underlying the matching engine can be flexibly changed by the enterprise's staff to set different ‘triggers’ for SA/customer interaction in accordance with changes in the enterprise's sales and marketing strategy. In the offline world, a customer's encounter in a given shopping environment with the sales personnel available at that location is random, at best. For example, if an affluent consumer from the 30328 area code in Atlanta, Ga. enters a local bank branch seeking a complicated mortgage re-finance product, he may or may not encounter an appropriate expert available in the store at that time. In addition, he may or may not encounter an SA who knows how to address the needs and buying habits of affluent consumers. By comparison, in the financial institution's virtual storefront, the bank can effectively make its entire sales force available to handle all of the traffic encountered at the e-commerce site, but parse that traffic out to the most suitable SAs depending upon an array of variables: the type of product, the psychographic and demographic characteristics of both the customer and the SA, the sales skills of the SA in that product category and the SA's demonstrated ability to close a sale online. As a result, the enterprise is empowered to create far better “matches” between customers and its sales personnel in the online environment than is possible in the real world.

The mismatches of SA to opportunity, either in terms of the product expertise of the sales associate, or of the demographic and/or psychographic characteristics of the consumer and the sales associate, are addressed by the present invention. The present invention addresses this by matching product-specific SAs with browsing consumers based on (i) available clickstream data that passes information to the system about the nature of the sales opportunity itself, (ii) demographic information about the customer, (iii) information about the proficiencies of the SAs in the enterprise's sales force (e.g., which ones sell well into these types of product opportunities to these types of customers) and (iv) the nature of the ‘triggers,’ or matching rules established by the enterprise.

After the matching engine performs the matching function, the SA can be linked to the customer in a variety of ways. First, the system can seek out the best qualified SA for a given opportunity; if that SA is not available, the matching engine will go to the next best qualified SA and so on until the customer is being helped. The matching engine can notify the SA of the opportunity even when he or she is not logged on, such as through a page or a call to the associate's telephone. Second, the matching engine can notify the top several SAs and let the SAs “race” to the customer.

Alternatively, the matching engine can simply provide the SAs with their matching score (or simply notify them, without necessarily providing their score, that they are eligible for a given engagement), and let the SAs decide whether to contact the customer (or let the SAs ‘race’ to the customer). This information is provided to the SA on a series of SA-facing pages (effectively, an SA desktop) that the SA can view to see, on a dynamic, real-time basis, the number and kind of browsing consumers that the SA is qualified under the system to approach. So, the SA can identify opportunities simply by being logged on to the system or the SA, with the enterprise's permission, can be contacted by the system when an appropriate opportunity for that agent is identified by the system.

In essence, the matching engine allows for “can” and “must” approaches, as established through the system by the enterprise (e.g., the vendor of a given product) that controls its operation. A “can” situation is defined by the system as one in which an agent may (permissively) approach a browsing consumer based on elements of the matching engine. A “must” situation is defined as one that the enterprise has defined as requiring an SA to approach (mandatory). The system allows both “can” and “must” scenarios to be executed, and for the parameters that define these scenarios to be established, weighted, ranked and then re-ranked based on actual performance.

The system can operate independently to the enterprise's online channel or be connected to the enterprise's CRM, eCRM or other marketing systems to obtain information about known customers (the system of course allows SAs to approach both customers who are known to the enterprise (such as through login information or a cookie) and customers who are, as far as the enterprise knows at the time of engagement, simply anonymous browsers). The system can also be connected to the enterprise's ERP system to obtain product and catalog data, such as alternative product or service choices, and any related products or services, as well as excess inventory, reduced prices, and any other packages controlled by the enterprise. This information is provided to the SA on the SA facing web pages.

An external data gathering engine allows the SAs to collect and repurpose, at the point of opportunity, collateral sales material (either from the enterprise or from third-party sources available on the Internet or from other sources) that may be helpful in the sales process. For example, an SA could perhaps locate an article on the Web from The Wall Street Journal that explains why now is the time to refinance; the SA might share that article with a browsing customer to convince the customer not to postpone the decision. A wide variety of data, both internal and external to the client enterprise, could be gathered that might prove helpful to closing the sale, including existing enterprise-provided sales and marketing materials, magazine articles, financial calculators, other competitors' web sites or competitive comparisons. The data gathering engine collects this information (as established in a baseline (i.e., initial) configuration), and as it has subsequently been used collectively throughout the enterprise's sales force), and then can recommend specific pieces of collateral information for use in conjunction with any particular opportunity to the SA via the SA facing web pages.

Additionally, the system includes a best practices engine that monitors the entire sales engagement in order to develop a database of what techniques and collateral sales material were successful and what were not successful in particular sales transactions. The best practices engine continually rates and re-ranks both SAs (in terms of the opportunities available to them) and collateral sales materials (again, on an opportunity-centric basis) on the basis of all activity captured by the system up to that moment. Accordingly, the system dynamically provides “up-to-the-minute” rankings and the most effective matches of both SAs and collateral sales material to any given opportunity. During a sales transaction, the SA is provided with these proven “best practices” via the SA facing web pages to assist the SA in closing the sale.

The system does not have to result in the “closing” of transactions purely through online interaction in order to be effective. For example, in a situation as complex as a mortgage transaction, it may be sufficient for the engagement to originate online at a browsing session, for the SA to achieve an introduction through a proactive chat session, for the session to bridge from chat to a PSTN conference call, for the agent to make an appointment with the consumer at a retail location and for the sale ultimately to be consummated face-to-face in a bank branch. Accordingly, the utility of the application is not limited to the online channel. Hence, the present invention also contemplates functionality that will allow a sales associate to first communicate with a consumer in chat, but also to bridge from the chat session to a telephonic conference call through the PSTN or via VOIP technology.

The system also continually monitors the sales process and provides this information as well as reports on consumers, SAs, and sales to the enterprise through enterprise facing web pages. This information can also be sent to offline databases maintained by the enterprise for corporate management purposes (for example, to an ERP or human resources system). The system can provide integrated SA compensation accounting, if necessary. Further, the system collects a robust database of customer purchasing patterns that provides valuable customer behavior data to the SAs and enterprises. This data drives future matchmaking (both in terms of agents and collateral sales data that are brought to bear on any given opportunity scenario), and also facilitates and informs future direct marketing and e-commerce initiatives. Therefore, the present invention will substantially enhance customers' online e-commerce experiences and materially increase the volume of sales made in, over, through, or in conjunction with online environments.

Virtually any enterprise that sells complex or consultative products or services and that has a website can benefit from the present invention. Many websites, such as auction sites and business to business exchange platforms, financial sites, travel sites, catering service sites, wholesale and retail sites, can benefit greatly from the present invention. Also, as noted above, there are benefits to the enterprise, in the form of additional data for managing the enterprise, that are effectively independent of the existence of the web site.

The online channel today is limited to merchandise that has certain commodity characteristics that are not so complex as to require sales people to close the sale. The present invention, by contrast, enhances the effectiveness of the online sales process particularly with respect to more complex, less commoditized offerings such as electronic equipment, automobiles, financial products (mortgages, car leases and other loans, insurance, wealth planning, mutual funds and securities), luxury products (such as fine food and wine, jewelry, cosmetics) and other merchandise and services that typically require a high-level of sales assistance. Thus, the present invention allows enterprises to substantially expand the categories of merchandise that can be effectively sold through or in conjunction with an online channel. Moreover, by allowing SAs to proactively approach browsers online, the present invention effectively allows enterprises to man their online presence with real people, who can then use the communication functionality offered through the present invention to address consumers' needs in real time, either for the purpose of closing the deal online or generating a ‘hot lead’ that can then be passed into the existing offline channel. Thus, the present invention effectively marries or bridges the online and offline selling processes, and allows the enterprise's existing “offline” human selling resources to be leveraged against online opportunities.

Online customer service solutions are expected to grow from a $162 million market in 1999 to $1.95 billion in 2004. Most such solutions are focused on the post-sale, eCRM space. The present invention, by contrast, focuses on sales as a discipline that is distinct from customer service. Moreover, the present invention addresses the online sales problem by matching real-time sales opportunities with experienced, accredited, knowledgeable sales personnel—in effect placing a human face into the online channel—and arming those personnel with opportunity-centric collateral sales material.

A major difference between current eCRM solutions and the present invention is that the present invention goes beyond existing CRM tactics by matching the customer with the best SAs for the customer's needs on an opportunity-centric and customer-centric basis, bringing the most appropriate SA to the opportunity, and then providing that SA with the necessary tools to complete the sale (both data assets and communication functionalities). This should be compared to current eCRM solutions that merely provide access to a call center representative who is inadequately trained to answer questions about products or suggest reasonable alternatives to the customer. By establishing personalized, human interaction as part of the sales process rather than waiting for a customer to ask for assistance, the present invention dramatically improves the e-commerce experience. Additionally, the present invention allows for an SA to have a relationship with the customer (rather than the “database” building a relationship with the customer), helping to facilitate a smoother transition (from a customer experience perspective) from a bricks and mortar purchasing experience. Further, the present invention provides an intelligent, personalized solution—not an artificially intelligent, mechanized solution. Finally, the present invention contemplates a series of real-time communication functionalities—chat, VOIP, streaming media and, importantly, the PSTN that bridge the online and offline channels and make the online experience far more robust from a selling perspective.

Perhaps the most compelling reason for increasing customer satisfaction by using SAs is to increase customer loyalty. Repeat customers visit a site twice as often and spend one-third more than the casual visitor. SAs can be expected to establish ongoing relationships with customers, increase spending per customer (the average sale amount today is $112 per transaction), as well as growing the number of repeat customers.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional diagram illustrating the external connectivity of a preferred embodiment of a system for linking sales associates with customers according to the present invention.

FIG. 2 is a functional diagram schematically illustrating the architecture of the system and the external connectivity of the system with an enterprise.

FIG. 3 is a flow diagram illustrating the registration and authentication process according to one embodiment of the present invention.

FIG. 4 is a flow diagram illustrating the training and accreditation process according to one embodiment of the present invention.

FIG. 5 is a flow diagram illustrating the matching process according to one embodiment of the present invention.

FIG. 6 is a screen shot of the Sales Office function of an SA user interface.

FIG. 7 is a screen shot of a Sales Floor function of the SA user interface.

FIG. 8 is a further screen shot of the Sales Floor function of the SA user interface.

FIG. 9 is a screen shot of a Certification function of the SA user interface.

FIG. 10 is a flow diagram of the sales process according to an embodiment of the present invention.

FIG. 11 is a flow diagram that reflects certain elements of the invention disclosed herein.

FIG. 12 is a flow diagram that reflects certain elements of the invention disclosed herein.

FIG. 13 is a flow diagram that reflects certain elements of the invention disclosed herein.

DETAILED DESCRIPTION

FIG. 1 shows the connectivity of an embodiment of the system 10 of the present invention to other entities. System 10 can interface with other external entities, sales associates (“SAs”) 214, enterprises 14, credit/background check agencies 16, enterprise related third parties 17, and unrelated third parties 18. System 10 is indirectly connected to customers 200 through the enterprise 14. System 10 matches a customer with the best qualified SA or SAs based on predetermined criteria and provides the SAs with sales tools and information to enable SAs via SA-facing web pages to ably assist customers to make purchases at the enterprise's website. Further communication between the SAs and customers is facilitated by the communication bridge 234. System 10 further provides enterprise-facing web pages to enable the enterprise to monitor the sales process.

An enterprise, as previously described, can be any organization or institution that engages in the selling of products, goods, or services of a complex nature. Retailers, insurance companies, real estate companies, auctions, professional services firms, travel agencies, financial institutions, stock brokers, and others similarly situated fit within the broad and limitless profile of organizations who utilize the systems and processes according to the present invention.

SAs can work for the enterprise, Captive SAs (CSA), or can be Independent SAs (ISA), who represent the same product or set of products as independent contractors for a number of different enterprises.

Examples of some enterprise related third parties 17 are the enterprise's CRM or eCRM system, the enterprise's ERP system, the enterprise's data mining/analytics/marketing platforms, the enterprise's human resources system, and the enterprise's inventory, accounting and other back office systems. Unrelated third parties 18 are parties that have relevant information to assist in the selling process, such as Consumer Reports, the Wall Street Journal and even conceivably a competitor's website (assuming a comparison of the primary vendor's offering with the competitor's offering will reflect favorably on the primary vendor's offering). Credit/background reporting services 16 are any service that provides information on a person's credit history, criminal record, and other personal background information. These services can be accessed to verify the identity of an SA or assist an enterprise in accrediting an SA (the latter function is particularly important insofar as the enterprise is engaging ISAs, who are unlikely to be known to the enterprise, as independent contractors). In CSA scenarios, this information will most likely be passed from the enterprise's ERP and/or HR system directly to the system.

System 10 may take the form of a network of desired systems, computers, or other functionality, located in one or more geographical locations, miming any desired operating systems and applications. In one embodiment, system 10 is J2EE compliant and is implemented on a Sun Microsystems, JAVA-based architecture and in another embodiment system 10 is implemented in a Linux-based system. System 10 may be connected to the sales associates 12, enterprises 14, credit/background check services 16, and enterprise related third parties 17 and any other desired entity via public or private packet switched or other data networks including the Internet, circuit switched networks, such as the PSTN, wireless network, or any other desired communications infrastructure 21. Server is used herein to refer to an application on an individual server or a portion of a server shared with other applications.

FIG. 2 illustrates schematically, in more detail, the connectivity and architecture of the system 10 when connected to a particular enterprise server 14. A customer 200 accesses a website at the enterprise server 14 via a web browser 202, such as Internet Explorer from Microsoft Corporation. As the customer is browsing the enterprise's website, the enterprise monitors the activities or session information of the customer 200. A session information message or messages, typically, but not necessarily, passed in XML format, are sent from the enterprise server 14 to an opportunity qualifier 204 in an engagement engine 205. Session information includes a variety of clickstream-derived data, such as, for example, whether the customer has requested assistance from an SA, whether the customer has indicated that it does not want assistance from an SA, the page on a website that the customer is viewing, and/or the goods or services the customer is examining on that page, demographic or other information about the customer extracted from the web page the customer is examining (such as the value of a mortgage that the customer is seeking, extracted from a mortgage calculator the customer is filling out), the contents of the customer's shopping cart, the time that the customer has looked at a given product on a given Web page, the customer's surfing pattern, the identity of the customer, and the customer's past purchasing history with this enterprise. The opportunity qualifier 204 may also receive customer information about the customer 200 from a enterprise's customer database 206 via a content engine 208. The content engine 208 accesses the customer database through, for example, the enterprise's eCRM system. The customer information may include some or all of the following information: the customer's name, address, past purchase information, past SAs used, items of interest, past site activity, and recommended purchases based on past purchasing history, if such information is available about the customer. Based on the session information and/or the customer information received, the opportunity qualifier 204 determines whether the customer is required to receive assistance from an SA (a “must” scenario) or is a potential target for permissive assistance from an SA (a “can” scenario).

If the opportunity qualifier 204 determines that the customer wants or could use help from an SA, the opportunity qualifier 204 sends an XML opportunity message to an Expert Sales Availability Choice Technology (“ExSACT”) matching engine 212. The opportunity information sent to the ExSACT matching engine 212 from the opportunity qualifier 204 includes session information and customer information.

An SA connects to the system 10 either through the enterprise's internal network (“intranet”) and/or through a web browser 216, such as Internet Explorer from Microsoft Corp. Before beginning to assist customers with specific goods or services, an SA must register with the system and must be accredited to sell the specific goods or services. An SA registers, trains and obtains certification via a skills engine 218. The Skills engine 218 may also receive performance data regarding SAs from the enterprise's existing ERP/HR systems 217. Performance data includes such things as the SA's performance ratings within the enterprise (based on an unlimited variety of performance criteria, including revenues, the SA's return or rescission rates, etc.), and any accreditations or licenses to sell certain products. This information on individual SAs is stored in the SA data base 219. The skills engine 218 also continually gathers information concerning sales transactions and the performance of the SAs within specific transactional contexts, and generates reports on the transactions as well as performance reports on the SAs. Such sales transaction information includes, for example, whether the sales transaction resulted in a sale, the amount of the sale, and the products sold or attempted to be sold. The skills engine 218 can include accounting applications to monitor the sales made over the system and manage the payment of SAs and invoicing of the enterprises. The system also includes applications that monitor and generate reports on the enterprises and customers and can be provided to the enterprise offline or online via enterprise facing web pages. If the system is used with independent SAs, the system connects with credit/background reporting services so that background and credit reports of the SA can be obtained. This information is likely not necessary with a captive SA.

Once an SA is online, registered, and certified, the SA can access the desktop 220. When an SA is logged into the desktop 220, the SA's profile information is sent to the ExSACT matching engine 212. An SA's profile information includes, for example, the SA's name, products or services accredited to sell by the system, and performance data with respect to the SA's performance using the system. The SA's profile information is continually updated by the system. Based on the profile information of the currently available SAs, customer information (if available), and session information, the matching engine creates an ordered list of available SAs best suited to assist the customer. The matching is done in a variety of enterprise- and system-specified ways, as explained in more detail below. The list of SAs is sent from the matching engine to the queue control 210 and the queue control ensures that an SA is paired up with the customer and that the SA responds to the opportunity.

The desktop 220 presents the SA with a communication user interface in the form of web pages through which the SA can monitor customers on the enterprise's website, interact with and assist the customers, interact with other SAs, and access various goods, services, best practices, and external information. The SA can take over the customer's navigation through the enterprise's website or can take the customer to a third party website. The collaboration feature can be provided by collaborative browsing tools from companies such as TogetherWeb, HipBone, and Cisco.

The desktop 220 receives product and catalog information from a product data base 224 via the content engine 208. The content engine 208 accesses the product data base 224 via, for example, the enterprise's ERP system. The types of product information include, for example, product specifications, collateral products (e.g., like products or product substitutes at varying price points), warranty information, product competitive data, comparative product information from other competitive enterprises and upsell and cross-sell information. The types of catalog information include, for example, inventory information (availability or backlog), pricing information, promotional or sale information, terms of sale, and commission information.

The desktop 220 receives external information from a caching database 225 via the content engine 208 and from a best practices database via a practices engine 230. The practices engine 230 collects and organizes in the caching database 225 and the best practices database 232 external materials such as product slicks, magazine articles, competitor comparisons, third-party financial calculators and comparison engines—essentially, any kind of information whether provided from the enterprise, from third parties and made available digitally (including information available on the Web) or from SAs in past selling situations (such as a good ‘pitch’ to use in a given sales scenario).

Product, catalog, and external information is gathered electronically, either passed from the product database 224 in the case of internal information, or, in the case of external information, generated from a baseline of external sources approved and established by the enterprise and captured through usage of the system over time. This information is then presented to the SA by the desktop 220. Product, catalog, and external information can be collectively referred to as sales information.

The desktop 220 receives best practices information from the best practices data base 232 via the practices engine 230. The practices engine 230 monitors all communication, data, external information, and resources (collectively “assets”) used by an SA during a sales encounter and for a particular product or service. All of this information is then cataloged by enterprise, vertical and/or product as well as scored based upon the outcome of each related sales interaction to formulate a set of best practices. The best practices information is then stored in the best practices data base 232. The practices engine 230 indexes all aspects of the sales transaction (e.g., text transcripts of online chat sessions, audio transcripts of voice over IP sessions and/or telephone sessions, browser driving, etc.) in a manner that allows the practices engine to point-deploy dynamic best practice detail against the specific parameters of each sales engagement. During a sale, an SA has access to these stored best practices and external information through the desktop 220 to assist closing the sale, as discussed below with reference to FIGS. 7 and 8. The practices engine builds a correlation between the assets used, the use of an asset in a given opportunity, and how many times the asset was used successfully. This information can also be provided to enterprises offline or via enterprise facing web pages on the desktop 220, as it provides them with valuable customer behavior data.

Further communication between SAs and customers is facilitated by communication bridge 234. Communication bridge 234 facilitates methods of communication such as by telephone, instant messaging, web collaboration, web conferencing, e-mail, and voice over IP. The telephony side of the communication bridge 234 is known in the art and made by such companies as J2 Global Communications and Z-Tel Communications and the instant messaging and web collaboration side of the communications bridge is known in the art and made by such companies as Cisco, TogetherWeb, and HipBone. The communication bridge 234 can be internal or external to the system 10. Through this communication bridge, a customer/SA sales engagement commenced in chat online can be bridged through such a third-party to a PSTN-based conference call. This bridge is established either by the SA providing the customer with a toll free number to call or by the customer providing the SA with the customer's telephone number so that the SA call establish a telephone call with the customer via the communications bridge 234. In that conference call, if the SA has access to both a phone line and the Internet, the SA and customer can communicate via voice, while still maintaining a co-browsing session on the Internet, i.e., the SA can talk to the customer while navigating the customer through the Internet.

FIG. 3 provides a flow diagram of the registration and authentication process according to one embodiment of the present invention. At 70, the Skills engine 218 receives a registration request. At 72, the Skills engine 218 unit determines if the requester is a registered SA by the SA entering a preselected username and password or other identification verification mechanism. If the SA is registered with the system, the Skills engine 218 logs the SA in and updates its records of online sales agents, as shown at 74. If the SA is not registered, the Skills engine 218 requests sales associate information from the SA, as shown at 76. The requested sales associate information may include personal (including a picture), historical, and other core data, such as, the name, address, and phone number of the sales associate, the job title and status of the sales associate, how many years the sales associate has been in this job or related jobs, the products the sales associate is interested in selling or is accredited to sell (this could be in ranked order), and the sales associate's preferred schedule. The skills engine may also request and receive some enterprise sales associate information on the sales associate. This enterprise sales associate information includes, for example, the SA's employment history, performance data on the SA (revenues, rescission rates, etc.), and the products the SA is accredited or licensed to sell. Sales associate information and enterprise sales associate information is collectively combined with any other SA performance data to create an SA profile on each sales associate. If this is a captive sales agent (CSA), the CSA may be required to include security information to establish that she can sell for the particular enterprise. Alternatively, a CSA for a particular enterprise can register via a enterprise-specific URL to determine the CSA relationship.

At 78, the sales associate information is received from the SA. For fraud protection, the Skills engine 218 may cause a request to be sent to a credit/background check agency as shown at 80. This request may be sent directly from the system to the agency online or may be done offline. As a result, the system will be able to authoritatively identify SAs and prevent expelled SAs from gaining re-admittance under an assumed name. At 82, the Skills engine 218 receives the credit and background check data from the agencies. Again this can be done online or can be done offline. The Skills engine can also receive enterprise SA information, such as, for example, product accreditation information, schedule information, and other relevant information and performance data on the sales associate from the enterprise. The Skills engine 218 analyses any credit and background check data, any enterprise sales associate information, and sales associate information at 84 to determine if the SA is an acceptable candidate. If not, at 86, the SA is sent a rejection. If the SA is acceptable, the SA is sent a notification of her acceptance, given further instructions about registering and about the system. The notices can be sent either online or can be sent offline. The SA then may provide the system with her schedule and contact preferences, for example, (i) only when online and “available,” (ii) off-line notification preferences, and (iii) off-line notification preferences based on SA-established schedule. At 89, the SA may be required to proceed to the training and accreditation process prior to completing the registration process based rules defined by the system or enterprise.

FIG. 4 illustrates a flow diagram of the training and accreditation process according to one embodiment of the invention. At 90, the Skills engine 218 receives a training or accreditation request from an SA. SAs may be accredited in terms of a merchandise category or a specific product or service. Accreditation standards can be created by the enterprise or the manufacturer, but in any event are published by the system. In response, at 92 the Skills engine 218 causes the appropriate materials to be provided to the SA. The materials can be provided to the SA online or can be sent to the SA offline. It is not necessarily objectionable that SAs could “cheat” the testing process by, for example, taking the test on an “open book” basis since they can also “cheat” in the same manner during the online sales experience. The materials could be established by the enterprises or by the manufacturers of certain products. The training materials contain the best practices information captured by the best practices engine 230 and enterprise supplied materials from the product data server 222. At 94, the Skills engine 218 receives and analyzes the results of the SA's training or accreditation and then at 95 the Skills engine 218 evaluates the observed performance metrics. At 96, the Skills engine 218 determines whether to accredit the SA. Then at 98, the Skills engine updates the SA records to indicate any new accreditation levels. Upon accreditation, the SA receives a “license” from the system or the enterprise to sell a specific good or service or category of goods or services. Licenses could also be granted on the basis of other categories as well, such as by geography, by demographic of the customer (reflected perhaps by customer login information or zip code information) or by any combination of the foregoing (e.g., by product and by demographic).

The testing and accreditation process can be performed online, manually, or a combination of both. The testing and accreditation process gives the system the ability to train and accredit SAs in order to effectively grant licenses to sell specific categories of products, goods, or services. Each enterprise can impose the training or certification level it desires before an SA will be permitted to sell at the enterprise's website.

Turning now to FIG. 5, the matching functionality of the ExSACT matching engine 212 assures that the most qualified SA or SAs are matched to each browsing opportunity that meets “can” or “must” scenarios as defined by the matching engine. The following description of the matching functionality is provided in terms of a captive SA and enterprise or enterprise specific matching, but it is equally applicable to an independent SA selling the same product or set of products as an independent contractor on behalf of a variety of different enterprises.

At 500, the opportunity qualifier 204 identifies a browsing session that represents a sales opportunity (based on session information and, if available, customer information). The opportunity context server 204 sends the matching engine a request for SA assistance based on the nature of those parameters. At 502, the matching engine determines the applicable rule set to apply to the matching. The rule set is determined by the product or service the customer is interested in or other “triggers” established by the enterprise (for example, the enterprise could instruct the system to find a qualified sales associate whenever a mortgage calculator involving an original principal balance of $300,000 is engaged). The applicable rule set is determined from page-to-product mapping 504, enterprise specific product hierarchy 506, and matching rules 505. Page-to-product mapping 504 decodes the URL information from the session attributes to determine what product the customer is looking at. The page-to-product mapping 504 could be part of the opportunity qualifier 204 or could be separate. The enterprise-specific product hierarchy is then used to determine if the product the customer is interested in has a corresponding rule set. If the specific product does not have a rule set, then the lowest applicable rule set is determined from the hierarchy. The appropriate rule set is then selected from the matching rules 505.

Once the appropriate rule set 503 is determined, at 508 the matching engine evaluates all SAs against the rules of the chosen rule set. First, at 509, an unordered list of qualified SAs is produced. The matching is dynamically performed by weighing customer information, session information, and SA profile information according to the rule set, and each qualified SA is given a matching score. The SA profiles are continually updated by the system to provide the most current information for the ExACT matching engine. The matching score is based on the relative ranking of each SA within the bounds of a particular rule multiplied by the relative importance of that rule among all the rules for a particular rule set. At 510, the matching engine ranks the SAs based on the resulting matching scores. A list is generated of qualified SAs in rank order at 512. The list is then sent to the queue control at 513 and the queue control 513 ensures that a SA from the list is paired up with the customer.

Depending on the enterprise's preference, the matching engine matches the customer with an available SA with the highest matching score and alerts the SA that she must contact the customer, alerts qualified SAs at the top of the generated list that a customer needs assistance, or simply provides the SAs with their matching score and lets the SAs decide whether to contact the customer. With the second option, the SAs then “race” to the customer and the first SA to respond assists the customer. The SAs, in all scenarios, are notified through the desktop communication user interface, instant messaging, e-mail, telephone, wireless device, and/or any other applicable means and may be provided with their matching score. If the pool of available SAs is low, the matching application can cause SAs to be contacted via instant messaging, e-mail, telephone, wireless device, and/or any other applicable means to get online. Again, the SAs are contacted through a variety of means.

In one embodiment, the desktop 220 provides a simple user interface, for example, enterprise-facing web pages, to the ExSACT matching engine 212 for the enterprise to change the matching rules, introduce new rules, or reweigh existing rules for the matching engine. The matching engine also dynamically changes the matching rules based on various factors, such as sales successes or changing market conditions. Through this dynamic ranking feature, the matching engine produces “up-to-the-minute” opportunity matching based on criteria established by the enterprise and the success of the SA base in using the system.

FIG. 6 illustrates a screen shot of the Sales Office section of the SA user interface. The Browsing Customers window 600 displays customers browsing for products that the SA is accredited to sell and that the matching application has matched the SA with. The SA can set the Browsing Customers window to display all customers looking at products, which the SA is accredited to sell, or just customers looking at specific products the SA is accredited to sell. SAs accredited to sell different products would see different views of the aggregate browsing activity at the enterprise's website. The Browsing Customers window 600 specifically displays, inter alia, the name of the customer, if this information is available, the SA's matching score for the customer, the number of clicks the customer has made, what the customer is currently viewing, and the amount of time the customer has been browsing.

The Inbox window 602 displays messages from customers along with the customers' names, type of message, and date received. The SA can create new messages or can reply to the customer's messages via the Inbox.

To the extent that data is available on the customers, the Customer Profile window 604 displays a list of these customers obtained from the customer data server 208. Basic information about the customer (such as address and phone number) is displayed and a menu of additional information, such as, relationship, correspondence, and personal notes, is displayed. By clicking on one of the menu items additional information is displayed in a More Detail window (not shown).

The top left hand side of the screen displays the various functions that are available to the SA at the Sales Office, for example, Daily Information, Browsing Customers, Product Resource Finder, Product Resource Library, Customer Profiles, and Inbox.

When an SA is linked with a customer, a Sales Floor screen is displayed on the SAs user interface as shown in FIGS. 7 and 8. The Sales Floor screen has a Session History window 700 that allows an SA to view the session history of the customer and view a current map of the customer in the website, the current flow of the customer, past maps, and past flows. A Customers Browser window 701 is also displayed on the Sales Floor screen that allows the SA to view what the customer is viewing. If allowed by the enterprise and/or the customer, an SA may manipulate and control the customer's browser and may ‘whiteboard’ on the pages the customer is viewing.

The Chat With Customer window 704 allows the SA to communicate with the customer. Instant messenger is the method of communication shown in the Customer Interaction window 704, as well as a list of commonly used phrases. The SA and customer can communicate via voice over IP, telephone, e-mail, or on a variety of applicable means. If the customer has the capability to receive a telephone call while connected to the Internet, the SA can connect to the customer via voice over IP or a telephone call over the PSTN through a bridge provided by the system. The customer can continue to view applicable web pages while conversing with the SA.

The Product Resource Finder 702 window allows the SA to select a particular product, for example, loans. The SA can, by clicking on a particular product, obtain additional product and catalog information concerning the product or service. The Product Resource Finder may also be used to assist the SA in identifying related products to be suggested as upsells or cross-sells. The SA can search for products or browse through categories of products. Information is provided to the Product Resource Finder window from the product database 224 via the content engine 208.

The Product Resource Library window 706 is used by the SA to access additional information about a particular product or service. In the example used in FIG. 8, the SA desires more information regarding mortgages. The Item Information window 706 provides the SA with best practices information from the practices engine 230. As explained above, the best practices information includes sales advice, external information, and product and catalog information, such as comparisons to other products, third party information regarding the product, sales pitches, related products, specific product information, warranty information, promotional information, shipping options, and terms of sale.

The Transaction Detail window 708 displays the customer's shopping cart to the SA. The SA, subject to the enterprise's and/or the customer's permission, can manipulate the customer's shopping cart.

FIG. 9 illustrates the Certification screen of the SA user interface. The Qualifications window 900 shows the SA the products and services that the SA is qualified to sell as well as the SAs rankings in her qualifications. The Certification Information window 902 provides the SA with information concerning the particular certifications available. The Certification detail window 904 provides the SA with an online test for certification.

FIG. 10 illustrates a flow diagram of the sales process using the system of the invention. At 1000, a customer enters a website. If the customer, is a returning customer of the website, the website greets the customer at 1002. The ExSACT matching engine 212 then matches the customer with a specific SA or several SAs. In step 1004, the SA greets the customer. This greeting is either re-active (if the customer has requested help) or pro-active (if the customer has not specifically requested sales assistance) depending on the customer's actions and the setup of the website. The SA evaluates the customer's intent at 1006 and determines whether the customer desires assistance at 1008. If the customer does not want assistance, the SA disengages at 1010.

If the customer does seek assistance, the SA then evaluates the customer's needs further through communication with the customer and accessing data on the customer at 1012. At this point, the SA determines the products, features, price range, user, and the customer's product knowledge. The SA then performs research at 1014 using the Product Resource Finder and Product Resource Library Information windows shown in FIG. 8 to access the best practices data. The SA directs the customer to specific products at 1016 and provides additional information as necessary to close the sale. The SA can use external (Web) assets as part of the experience, for example, the SA can take the customer to a competitor's website to show the customer the higher prices being charged by the competitor.

The SA evaluates whether the customer made a selection at 1018 and if so suggests related merchandise at 1022. The SA can then perform research at step 1014 on the related merchandise and then the process continues as before. If the customer did not make a selection, the SA further evaluates whether the customer is finished shopping at 1020. If the customer is not finished shopping, the SA evaluates the needs of the customer further at 1012 and the process continues as before. If the customer is finished shopping, the SA offers additional product information at 1024 and reinforces the customer's selection at 1026. The customer proceeds to the enterprise specific check out process at 1028. The SA can assist the customer at the check out process. At 1030, a satisfied customer leaves the website. The SA can follow up with the customer through the methods shown at the bottom of FIG. 10.

FIG. 11 is a flow diagram steps performed at an accounting unit. As depicted at 160, data is received regarding sales transactions. At 162, sales transactions are recorded. At 164, commission payments are calculated based on sales transactions. At 168, data is input into SA's record regarding sales. At 166, a bill retailer is provided with the calculations at 164.

FIG. 12 is a flow diagram depicting operations performed at a real time monitoring unit. Sales activity is monitored at 170. Customer feedback is obtained, as shown at 174. Sales activity is evaluated at 172. At 176, data regarding sales activity is inputted into SA's records. At 178, data regarding sales activity is sent to a data warehouse.

FIG. 13 indicates example operations involving a sales associate (SA) in accordance with the present disclosure. At 180, registration occurs. At 182, a background check 182 on the SA is conducted. If the SA fails the background check, the SA is banned from the system, as shown at 184. If the SA passes the background check at 182, a log-in is performed at 186. At 188, training and accreditation are provided. A link with a customer is formed at 190. At 200, communication with a customer occurs. At 202, a sale is either closed or ended. At 204, the SA performs a log-out.

The foregoing is provided in order to disclose the invention in accordance with the patent laws, and more particularly to disclose preferred embodiments of systems and processes according to the present invention. Modifications, adaptations, and changes may be made to what is disclosed without departing from the scope or spirit of the invention, which is to provide systems and processes to facilitate selling on, over, through or in conjunction with the online channel. 

1. A method for selling goods and services in conjunction with the Internet, comprising: receiving session information from an enterprise's website about a customer's session on the website, the session information comprising the products the customer is searching; receiving any customer information on the customer from the enterprise; determining from the session information and any customer information that the customer constitutes a sales opportunity appropriate for assistance from a sales associate; matching the customer with at least one sales associate; facilitating communication for a sales transaction between the customer and the matched sales associate via the Internet; receiving sales information; and providing the session, customer, and sales information to the matched sales associate based on the particular sales opportunity with the customer. 2-62. (canceled) 